AFUS Dog Transformations, Force TSV Column Order, Process AfusOwner Data#227
Open
AFUS Dog Transformations, Force TSV Column Order, Process AfusOwner Data#227
Conversation
… of columns for a given table. Refactored the code that maintains the list of columns - switched from a set to a list to maintain order. Simplified the logic that was determining when to pull out PK columns to the front of a file since we should only do that when running with the Firecloud option. For default output, the column order in the data models for each table already has the PKs at the front of the table.
…ers, arm generator logic. Need to update standardDirectives and dateFilters if any are to be implemented (check w/ Matt). Added unit and integration tests for the new extraction pipeline.
Removing bad test cases (will not hold up over time).
Reducing idBatchSize to 10 to prevent overloading RedCap. Updated tests, removed debugging changes.
…r table was added as well. Created a new TransformationHelper function to process AFUS records where data for a single record is spread across multiple arms. Added tests: pipeline test, unit tests for the owner transformations, and new transformation helper method.
Updated unit tests to make sure we are trimming whitespace.
…e value as a long"
Added schema, pipeline builder, and transformation scripts for afus_dog. Added AfusDogDemographics and AfusDogResidence transformation.
…consistent failures. Extended transformation pipeline tests.
Refactored a common TransformationLog file to encapsulate the errors and warnings for all surveys and updated imports.
…-1958-afus-dog-merged
…sformations' into qh-dspdc-1958-afus-dog-merged
…t transform to retain incomplete records. Implementing VIP exclusion filters. Adding DAP pack filters to eols and sample pipelines.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
DSPDC-1958.
We would like to maintain the order of the original data model (schema) for columns in the final TSVs.
We also need to process afus_owner data and generate a TSV.
Extraction and transformation pipeline for the afus_dog tables.
This PR
Combined changes from branches qh-dspdc-1958-afus-dog and qh-force-tsv-column-order.
Added forms needed for afus_dog extraction.
Added schema fragments, pipeline builder, and transformation scripts for afus_dog.
Extends the tsv_convert script to process afus_owner.
Forces the column order to hardcoded lists for tsv column order.
Checklist